home *** CD-ROM | disk | FTP | other *** search
- Path: newshost.williams.edu!not-for-mail
- From: 96kfd@williams.edu (der tanzende Tigger)
- Newsgroups: comp.lang.c++
- Subject: tracing "new" memory problems
- Date: 6 Jan 1996 13:41:46 -0500
- Organization: Williams College, Williamstown MA
- Message-ID: <4cmfpaINN3hb@bigbird.cc.williams.edu>
- NNTP-Posting-Host: bigbird.cc.williams.edu
-
- I am writing an application that uses new and delete extensively, and
- it is very brittle: small changes (one more line read from a file in
- one place) cause large memory errors (a routine that read 120 lines
- from another file crashes on the sixth with "out of virtual memory in
- new"). In each case, an object is created when a line is read, and the
- memory is allocated using new.
-
- The problem is that my debugger (gdb) will not give me any more
- information than "exited with error"--no backtrace, no indication
- where the error occurred. The application was compiled with gcc 2.7.2
- on a Sun Sparc with SunOS 4.1.3_U1 and libg++. Is there any way to
- trace memory allocation in an application that crashes like this?
-
- Incidentally: my IPX has 16 mb of memory and 40 mb of virtual memory.
-
- --kd
-
-
-